-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge beta 22.1.0.2 #20527
Merge beta 22.1.0.2 #20527
Conversation
… UIView or a UIBarButtonItem
…elease_1.92.1 Integrate gutenberg-mobile release 1.92.1
…iOS into fix/20487-reader-crash-when-wtapping-more-share-button
* [**] [internal] Refactored Google SignIn implementation to not use the Google SDK [#20128] | ||
|
||
22.1 | ||
----- | ||
* [**] [internal] Refactor updating account related Core Data operations, which ususally happens during log in and out of the app. [#20394] | ||
* [***] [internal] Refactor uploading photos (from the device photo, the Free Photo library, and other sources) to the WordPress Media Library. Affected areas are where you can choose a photo and upload, including the "Media" screen, adding images to a post, updating site icon, etc. [#20322] | ||
* [**] [WordPress-only] Warns user about sites with only individual plugins not supporting core app features and offers the option to switch to the Jetpack app. [#20408] | ||
* [**] [internal] Refactored Google SignIn implementation to not use the Google SDK [#20128] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As mentioned in the PR description, this entry was in 22.1 because that's where the PR was meant to land after code freeze but I fumbled and it landed on trunk
instead.
@@ -0,0 +1 @@ | |||
No updates this week. In the meantime, we're just over here cooling our jets. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not ru
🤔
@@ -0,0 +1 @@ | |||
No updates this week. In the meantime, we're just over here cooling our jets. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not es-ES
🤔
There were conflicts on `Podfile` and `Podfile.lock` because `release/22.1` and `trunk` both changed the Gutenberg version. As usual, I resolved them with `git checkout --theirs`, keeping the value from `trunk` under the assumption that the latest version of Gutenberg, 1.93.0-alpha2, is what `trunk` needs to work and that if the 1.92.1 hotfix hasn't already been integrated in the latest release, it will be soon and the Gutenberg team will followup with a new version update on `trunk`. There was also a conflict on the `RELEASE-NOTES.txt` that GitHub picked up with its more refined conflicts engine and that auto-merge didn't address properly but that I manually fixed. That was due to `release/22.1` adding new release note entries – which will not make it into the App Store release notes – in the 22.1 section and `trunk` having #20128 editing that section, too. #20128 was meant to land on `release/22.1` but I forgot to update the base branch after starting the code freeze 🤦♂️😭 Also, the entry about the personalize home tab had been removed on `trunk` via ec8a377. The release notes editor was notified about it, #20483 (review) ``` <<<<<<< release/22.1 -- Incoming Change * [**] Add a "Personalize Home Tab" button to the bottom of the Home tab that allows changing cards visibility. [#20369] * [*] [Reader] Fix an issue that was causing the app to crash when tapping the More or Share buttons in Reader Detail screen. [#20490] * [*] Block editor: Avoid empty Gallery block error [WordPress/gutenberg#49557] ======= * [**] [internal] Refactored Google SignIn implementation to not use the Google SDK [#20128] >>>>>>> trunk -- Current Change ```
c214ba2
to
011c8c3
Compare
* [*] [Reader] Fix an issue that was causing the app to crash when tapping the More or Share buttons in Reader Detail screen. [#20490] | ||
* [*] Block editor: Avoid empty Gallery block error [https://github.com/WordPress/gutenberg/pull/49557] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mentioned in PR that these won't make it to the App Store:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the the detailed PR description @mokagio. The way you addressed the issues makes sense to me.
📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.
|
📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.
|
Supersedes #20525, which I was too quick at opening and didn't realize had conflicts with
trunk
.Includes:
gutenberg-mobile
release 1.92.1 by @dcalhounRelease checks
.strings
and Fastlane metadata) automatically pulled for the new translations that have already been approved in GlotPress.xcconfig
Conflicts
There were conflicts on
Podfile
andPodfile.lock
becauserelease/22.1
andtrunk
both changed the Gutenberg version.As usual, I resolved them with
git checkout --theirs
, keeping the value fromtrunk
under the assumption that the latest version of Gutenberg, 1.93.0-alpha2, is whattrunk
needs to work and that if the1.92.1 hotfix hasn't already been integrated in the latest release, it will be soon and the Gutenberg team will followup with a new version update on
trunk
.There was also a conflict on the
RELEASE-NOTES.txt
that GitHub picked up with its more refined conflicts engine and that auto-merge didn't address properly but that I manually fixed.That was due to
release/22.1
adding new release note entries – which will not make it into the App Store release notes – in the 22.1 section andtrunk
having #20128 editing that section, too. #20128 was meant to land onrelease/22.1
but I forgot to update the base branch after starting the code freeze 🤦♂️😭